home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
The Arsenal Files 6
/
The Arsenal Files 6 (Arsenal Computer).ISO
/
os2
/
blt2_205.zip
/
README
< prev
next >
Wrap
Text File
|
1995-09-09
|
2KB
|
45 lines
Bullet/2 README 9-Sep-1995-chh.
Installation instructions.
Shareware Installation:
Copy all package files to the directory you want to install to. The
subdirectory src\ is created from the unzip process and contains the
source code of the demo program, blt2demo.exe. Additional source code
is in the online manual itself. The printer-ready manual is an API
reference manual for Bullet, and does not contain all that is in the
online version.
From the install directory, do:
C>install
The installer asks a question, then converts the bullet2.dl_ to the
dynamic link library BULLET2.DLL. No INI files are written or used.
Place BULLET2.DLL in a directory pointed to by your LIBPATH= statement
in config.sys; the first real path being the best. This allows the DLL
to be automatically loaded whenever your programs use BULLET/2.
Distribution and other license restrictions are detailed in the online
manual. Use VIEW.EXE which comes with OS/2 to view the manual (type
C>help VIEW if you need more information). Do not combine the
online manual with any other online manual.
Order forms are included in the package (!ORDER.*), with detailed
ordering instructions provided in the online manual.
To use the Bullet library code, you will need to link with the
bullet2i.lib import library, or use a .DEF file (the DLL exports
'BULLET'). See your linker documentation if more information is
required.
If you have any installation problems with getting Bullet to work with
your compiler, you may e-mail me at cornel@crl.com for installation help.
See the PRODUCT SUPPORT section in the manual for alternate support methods.
Sorry, but this free support is only for Bullet installation. Any other
type of support requires that you be a licensed, registered user.
What should be complete information on all aspects of Bullet's use is in
the online manual, with the API in printer-ready form. Check there
before anywhere else.